…ugin removal (#43492)

# Why

PR #43312 removed the legacy Android plugin in expo-modules-core, and made associated changes to the Gradle scripts in expo-go and in the create-expo-module templates.

Because of the potential to break many existing native modules when a project was upgraded to SDK 55, that PR was reverted.

However, what we should be doing is reverting only the changes in expo-modules-core, but leaving in place the changes in expo-go and create-expo-module templates that move to the newer Gradle plugin. This way, Expo Go and any new native modules created in future, will correctly use the new plugin.

# How

Restored only changes in expo-go and in the module templates, leaving expo-modules-core unchanged.

# Test Plan

CI (including Expo Go CI) should pass

`npm access grant` requires OTP but had no `--otp` flag or retry
handling, so grants would silently fail if the OTP expired between
publish and grant.

Shared packages like babel-preset-expo, jest-expo, and @expo/config are
depended on by nearly every package in the monorepo, so publishing them
would cascade a prompt to republish dozens of packages unnecessarily.
These packages are now excluded from dependent cascading by default.
Use --cascade-all to restore the previous behavior.

Shows which PRs labeled for an SDK version still need cherry-picking
to the SDK branch. Detects cherry-picks by matching PR numbers in
commit subjects, and publish status by cross-referencing "Publish
packages" commits with the packages each PR touched.

Usage: et csp [sdk] [--all] [--no-links]